We just migrated from 2003 to 2010, and now on to 2013.  I have Exchange 2013 CU3 installed, and all mailboxes moved.  When trying to move the public folders, I'm getting an error about DataValidationException.  Property expression <PF Name with spaces> isn't valid......

Many articles refer to a mail-enabled public folder with spaces can't have spaces in the alias.  This is NOT a mail-enabled public folder, so there isn't an alias that I can find.

Any ideas?

Thanks!

--Kent

Hi Kent,

Based on the error it looks like it mostly appears to be with any special characters or space in PF which causes to happen
First ensure that you do not have any space special characters in any of the public folder.If not correct it first

Run the below command to check the migration statistics
get-publicfoldermigration
get-publicfoldermigrationstatistics
You can start the migration again after correcting the folder characters.

Or you can Follow the below steps

Remove the current migration request
Get-PublicFolderMigrationRequest | Remove-PublicFolderMigrationRequest -Confirm:$false

Create new Migration Request
New-PublicFolderMigrationRequest -SourceDatabase (Get-PublicFolderDatabase -server mdntemp) -csvdata (Get-content C:\PFMigration\PFmap.csv -encoding byte) -BadItemLimit 500 -AcceptLargeDataLoss

Please mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you.

Regards,
Sathish

So the space in the name is not OK, even when it's not mail-enabled?  There have been spaces in the name since 2003, but you have to rename them in 2013?

What is the best way to rename them?

--Kent

Any feedback?

So the space in the name is not OK, even when it's not mail-enabled?  There have been spaces in the name since 2003, but you have to rename them in 2013?

What is the best way to rename them?

--Kent

Nopp, There is no need to remove spaces is the names. Having them is absolutely OK.
Pls post the exact error message you get.

Hi Kent,

Do you receive the error report in APP log like below?

Error: Property expression "ABC Room" isn't valid. Valid values are: Strings formed with characters from A to Z (uppercase or lowercase), digits from 0 to 9, !,..

If so, I think we can change the Alias from ABC Room to ABCRoom. This worked once for one of my customer.

Thanks,

Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnsfl@microsoft.com

I believe aliases are only available in mail-enabled public folders.  

Here is the exact message:

RunspaceId                       : 7fdb2174-e04a-4950-be57-6c0e77c4c02b
Name                             : PublicFolderMigration
Status                           : Failed
StatusDetail                     : FailedOther
SyncStage                        : CreatingFolderHierarchy
Flags                            : IntraOrg, Pull, Suspend, SuspendWhenReadyToComplete
RequestStyle                     : IntraOrg
Direction                        : Pull
Protect                          : False
Priority                         : Normal
Suspend                          : True
SourceVersion                    : Version 14.3 (Build 123.0)
SourceDatabase                   : Public Folder Database 0592897580
SourceServer                     : MYEXCHTEMP.mydomain.local
BatchName                        : 
OutlookAnywhereHostName          : 
RemoteCredentialUsername         : 
AuthenticationMethod             : Basic
RemoteMailboxLegacyDN            : 
RemoteMailboxServerLegacyDN      : 
BadItemLimit                     : 0
BadItemsEncountered              : 0
LargeItemLimit                   : 0
LargeItemsEncountered            : 0
FolderToMailboxMap               : {\}
QueuedTimestamp                  : 1/20/2014 8:36:49 PM
StartTimestamp                   : 1/20/2014 8:36:56 PM
LastUpdateTimestamp              : 1/20/2014 8:36:59 PM
InitialSeedingCompletedTimestamp : 
FinalSyncTimestamp               : 
CompletionTimestamp              : 
SuspendedTimestamp               : 
OverallDuration                  : 1.11:22:26
TotalFinalizationDuration        : 
TotalDataReplicationWaitDuration : 
TotalSuspendedDuration           : 
TotalFailedDuration              : 1.11:22:16
TotalQueuedDuration              : 00:00:04
TotalInProgressDuration          : 00:00:05
TotalStalledDueToCIDuration      : 
TotalStalledDueToHADuration      : 
TotalStalledDueToReadThrottle    : 
TotalStalledDueToWriteThrottle   : 
TotalStalledDueToReadCpu         : 
TotalStalledDueToWriteCpu        : 
TotalStalledDueToReadUnknown     : 
TotalStalledDueToWriteUnknown    : 
TotalTransientFailureDuration    : 
TotalIdleDuration                : 00:00:01
MRSServerName                    : 
EstimatedTransferSize            : 0 B (0 bytes)
EstimatedTransferItemCount       : 0
BytesTransferred                 : 0 B (0 bytes)
BytesTransferredPerMinute        : 
ItemsTransferred                 : 0
PercentComplete                  : 10
PositionInQueue                  : 
PreventCompletion                : True
FailureCode                      : -2146233088
FailureType                      : DataValidationException
FailureSide                      : Target
Message                          : Error: Property expression "my Office Schedule" isn't valid. Valid values are: 
                                   Strings formed with characters from A to Z (uppercase or lowercase), digits from 0 
                                   to 9, !, #, $, %, &, ', *, +, -, /, =, ?, ^, _, `, {, |, } or ~. One or more 
                                   periods may be embedded in an alias, but each period should be preceded and 
                                   followed by at least one of the other characters. Unicode characters from U+00A1 to 
                                   U+00FF are also valid in an alias, but they will be mapped to a best-fit US-ASCII 
                                   string in the e-mail address, which is generated from such an alias.
FailureTimestamp                 : 1/20/2014 8:36:59 PM
IsValid                          : True
ValidationMessage                : 
OrganizationId                   : 
RequestGuid                      : 447ed7f5-3e13-4e3c-8654-c202ba040030
RequestQueue                     : Mailbox Database 1159688983
ExchangeGuid                     : b62af075-26c1-4636-8273-8aa94ec4725f
Identity                         : 2616f69b-d3b3-48d5-85fc-25cf0cea9860\447ed7f5-3e13-4e3c-8654-c202ba040030
DiagnosticInfo                   : 
Report                           : 1/20/2014 8:36:49 PM [myexch01] 'mydomain.local/my/Administrators/Kent Iler' 
                                   created request.
                                   1/20/2014 8:36:54 PM [myexch01] The Microsoft Exchange Mailbox Replication service 
                                   'myexch01.mydomain.local' (15.0.775.35 caps:3F) is examining the request.
                                   1/20/2014 8:36:55 PM [myexch01] Connected to target mailbox 
                                   'b62af075-26c1-4636-8273-8aa94ec4725f', database 'Mailbox Database 1159688983', 
                                   Mailbox server 'myEXCH01.mydomain.local' Version 15.0 (Build 775.0), proxy 
                                   server 'myexch01.mydomain.local' 15.0.775.35 caps:07FFCB07FFFF.
                                   1/20/2014 8:36:55 PM [myexch01] Connected to source mailbox '', database 'Public 
                                   Folder Database 0592897580', Mailbox server 'myEXCHTEMP.mydomain.local' Version 
                                   14.3 (Build 123.0).
                                   1/20/2014 8:36:55 PM [myexch01] Request processing started.
                                   1/20/2014 8:36:57 PM [myexch01] Stage: CreatingFolderHierarchy. Percent complete: 
                                   10.
                                   1/20/2014 8:36:57 PM [myexch01] Initializing folder hierarchy from mailbox '': 33 
                                   folders total.
                                   1/20/2014 8:36:57 PM [myexch01] Folder creation progress: 0 folders created in 
                                   mailbox 'b62af075-26c1-4636-8273-8aa94ec4725f'.
                                   1/20/2014 8:36:59 PM [myexch01] Fatal error DataValidationException has occurred.
                                   
ObjectState                      : New

Even though it was NOT a mail-enabled folder, the mailNickname under ASDI Edit had to have spaces removed.  I assume this is similar if not the same as the Mail alias.  However, the EMC commands that have been given to remove invalid characters in mail-enabled folders do not work since this isn't mail-enabled.

The solution was to use ASDI Edit on the 2010 server, and go to:
DC=<domain>, CN="Microsoft Exchange System Objects"

For each Public Folder with a space, right click on it and go to the "mailNickname" attribute and remove the spaces.  Click OK, then run the command on the Exchange 2013 EMC:

Get-PublicFolderMigrationRequest | Resume-PublicFolderMigrationRequest

All public folders were migrated, and then you can continue with step 7 in this article:
http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx

Good luck, and thanks for all that tried to help, even though this ended up being the solution!

--Kent

• Marked as answer by Kent Iler Thursday, January 23, 2014 12:37 AM

So I have ran into the same problem with a client that has a lot of public folders, well over two hundred entries in the Public Folders to do it manually would be a very time intensive process. So I'm hoping that someone has a way to script this process or another way to remove the blank spaces in a bulk process of some kind.

Thanks in Advance,

Joe

Here it is

First verify the objects which has spaces:

$pfs= Get-publicfolder \ -recurse | where {$_.MailEnabled -eq True} | Get-MailPublicFolder | where {$_.alias -like * * -or $_.alias -like *,*}

you should see the results and than run the following to remove spaces.

foreach($pf in $pfs) {set-mailpublicfolder $pf.Identity -Alias:($pf.alias -replace \s|\,,)}

--HS

• Edited by HS' Thursday, January 08, 2015 8:50 PM

Hi!

Is it possible just to clear mailNickname property?

I've got ~1000 entries with russian names, which are not acceptable.